CruiseControl.NET : Project Configurable Build Plugin
This page last changed on Jun 08, 2005 by mroberts.

Most Build Plugins can be configured to be used only for certain projects. If they can be, it will say on their own documentation page.

A Build Plugin by default will appear on the Build Plugins list for all projects, but you can specify either a specific inclusion or exclusion list. These are described below. You cannot have both an inclusion and an exclusion list (if you do, you will get a configuration exception.)

Example

The name of the plugin (myBuildPlugin) is just an example - it will actually be the name of the specific type of Build Plugin you are using. Also, the other property shown (myBuildPluginsOwnProperty) is just an example of where the plugin-specific properties would go.

By default, you don't have to specify either an <includedProjects /> or <excludedProjects /> section, in which case your Build Plugin will be shown for all projects.

<myBuildPlugin myBuildPluginsOwnProperty="Something">
    <includedProjects>
        <projectName>My Project</projectName>
        <projectName>My Other Project</projectName>
    </includedProjects>
</myBuildPlugin>

OR

<myBuildPlugin myBuildPluginsOwnProperty="Something">
    <excludedProjects>
        <projectName>My Project</projectName>
        <projectName>My Other Project</projectName>
    </excludedProjects>
</myBuildPlugin>

Configuration Elements

Node Description Type Required Default
includedProjects OR excludedProjects A list of project names. If you use an <includedProjects> section the build plugin will only appear for those projects. If you use an <excludedProjects> section the build plugin will appear for all projects apart from the specified ones. In both cases, the project names must match exactly to those specified in your build server config files, including use of spaces and capital letters string list no empty lists for both sections, plugin used for all projects.
Document generated by Confluence on Jun 26, 2005 17:22